Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rollup of 3 pull requests #66629

Closed
wants to merge 7 commits into from

Conversation

pietroalbini
Copy link
Member

Successful merges:

Failed merges:

r? @ghost

pietroalbini and others added 7 commits November 20, 2019 10:33
…ed vec.

I based this solution on my reading of:

https://rethinkdb.com/blog/make-debugging-easier-with-custom-pretty-printers#what-is-still-to-be-done

That post claims that there is no clean way to check for garbage pointers, and
so this PR adopts the same solution of tentatively attempting to convert a
dererence to a string, which throws a clean exception on garbage that we can
catch and recover from.

I only made the change to vec and not the other pretty printers because I wanted
to focus my effort on the simplest thing that would resolve issue rust-lang#64343. In
particular, I *considered* generalizing this fix to work on the other datatypes
in the pretty-printing support library, but I don't want to invest effort in
that until after we resolve our overall debugging support strategy; see also
issues rust-lang#60826 and rust-lang#65564.
Some environment variables (like DEPLOY or DEPLOY_ALT for dist builders,
or IMAGE on Linux builders) are set on a lot of builders, and whether
they should be present or not can be detected automatically based on the
builder name and the platform.

This commit simplifies the CI configuration by automatically setting
those environment variables.
Fixes rust-lang#66476 by turning the violating example into an explicit
counterexample.
Document pitfall with `impl PartialEq<B> for A`

Fixes rust-lang#66476 by turning the violating example into an explicit
counterexample.
GitHub Actions: preparations, part 1

This PR adds the first batch of commits in preparation for GitHub Actions:

* Added GitHub Actions support in `src/ci/shared.sh` and bootstrap.
* Addded a `setup-environment.sh` script which guesses and sets the `DEPLOY`, `DEPLOY_ALT` and `IMAGE` environment variables automatically, to reduce the verbosity of the CI configuration.

This PR does **not** yet add any builders on GitHub Actions.

r? @alexcrichton
…r, r=alexcrichton

made gdb pretty-printing more robust when printing uninitialized vec

made gdb pretty-printing more robust when printing uninitialized vec

I based this solution on my reading of:

https://rethinkdb.com/blog/make-debugging-easier-with-custom-pretty-printers#what-is-still-to-be-done

That post claims that there is no clean way to check for garbage pointers, and
so this PR adopts the same solution of tentatively attempting to convert a
dererence to a string, which throws a clean exception on garbage that we can
catch and recover from.

I only made the change to vec and not the other pretty printers because I wanted
to focus my effort on the simplest thing that would resolve issue rust-lang#64343. In
particular, I *considered* generalizing this fix to work on the other datatypes
in the pretty-printing support library, but I don't want to invest effort in
that until after we resolve our overall debugging support strategy; see also
issues rust-lang#60826 and rust-lang#65564.

Fix rust-lang#64343
@pietroalbini
Copy link
Member Author

@bors r+ p=3 rollup=never

@bors
Copy link
Contributor

bors commented Nov 22, 2019

📌 Commit 07ddc51 has been approved by pietroalbini

@bors bors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Nov 22, 2019
@pietroalbini pietroalbini added the rollup A PR which is a rollup label Nov 22, 2019
@bors
Copy link
Contributor

bors commented Nov 22, 2019

⌛ Testing commit 07ddc51 with merge c02df086343793229ff6a16f333fb6fe9769aea9...

@rust-highfive
Copy link
Collaborator

Your PR failed (pretty log, raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log.
2019-11-22T13:49:09.0471515Z do so (now or later) by using -b with the checkout command again. Example:
2019-11-22T13:49:09.0471871Z 
2019-11-22T13:49:09.0472141Z   git checkout -b <new-branch-name>
2019-11-22T13:49:09.0473696Z 
2019-11-22T13:49:09.0473872Z HEAD is now at c02df0863 Auto merge of #66629 - pietroalbini:rollup-mbxzl5c, r=pietroalbini
2019-11-22T13:49:09.0882325Z ##[section]Starting: Setup environment
2019-11-22T13:49:09.0994756Z ==============================================================================
2019-11-22T13:49:09.0994880Z Task         : Bash
2019-11-22T13:49:09.0994987Z Description  : Run a Bash script on macOS, Linux, or Windows
---
2019-11-22T13:49:10.9205234Z 
2019-11-22T13:49:10.9205402Z 
2019-11-22T13:49:10.9205527Z 
2019-11-22T13:49:10.9205647Z 
2019-11-22T13:49:10.9205854Z  - #66566 (Document pitfall with `impl PartialEq<B> for A`)
2019-11-22T13:49:10.9206045Z  - #66569 (GitHub Actions: preparations, part 1)
2019-11-22T13:49:10.9206260Z  - #66576 (made gdb pretty-printing more robust when printing uninitialized vec)
2019-11-22T13:49:10.9206633Z AGENT_DISABLELOGPLUGIN_TESTFILEPUBLISHERPLUGIN=true
2019-11-22T13:49:10.9206832Z AGENT_DISABLELOGPLUGIN_TESTRESULTLOGPLUGIN=true
2019-11-22T13:49:10.9207013Z AGENT_HOMEDIRECTORY=C:\agents\2.160.1
2019-11-22T13:49:10.9207241Z AGENT_ID=518
---
2019-11-22T13:49:10.9224534Z BUILD_SOURCEBRANCHNAME=auto
2019-11-22T13:49:10.9224633Z BUILD_SOURCESDIRECTORY=D:\a\1\s
2019-11-22T13:49:10.9225038Z BUILD_SOURCEVERSION=c02df086343793229ff6a16f333fb6fe9769aea9
2019-11-22T13:49:10.9225144Z BUILD_SOURCEVERSIONAUTHOR=bors
2019-11-22T13:49:10.9225256Z BUILD_SOURCEVERSIONMESSAGE=Auto merge of #66629 - pietroalbini:rollup-mbxzl5c, r=pietroalbini
2019-11-22T13:49:10.9225455Z CI_JOB_NAME=i686-msvc-1
2019-11-22T13:49:10.9225526Z COBERTURA_HOME=C:\cobertura-2.1.1
2019-11-22T13:49:10.9225628Z COMMONPROGRAMFILES=C:\Program Files\Common Files
2019-11-22T13:49:10.9225714Z COMMON_TESTRESULTSDIRECTORY=D:\a\1\TestResults
---
2019-11-22T13:53:56.1559159Z  there is nothing to do
2019-11-22T13:53:56.1559471Z :: Starting full system upgrade...
2019-11-22T13:53:56.2248927Z  there is nothing to do
2019-11-22T13:53:56.2812182Z kill: 1703: No such process
2019-11-22T13:53:57.1653974Z PATH environment variable does not have C:\tools\msys64 in it. Adding...
2019-11-22T13:53:57.5814484Z Environment Vars (like PATH) have changed. Close/reopen your shell to
2019-11-22T13:53:57.5815016Z  see the changes (or in powershell/cmd.exe just type `refreshenv`).
2019-11-22T13:53:58.1786587Z   Software installed to 'C:\tools\msys64'
2019-11-22T13:53:58.2489434Z 
2019-11-22T13:53:58.2490729Z Chocolatey installed 1/1 packages. 
2019-11-22T13:53:58.2491107Z  See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
---
2019-11-22T13:53:59.0909928Z ========================== Starting Command Output ===========================
2019-11-22T13:53:59.0915614Z [command]"C:\Program Files\Git\bin\bash.exe" --noprofile --norc /d/a/_temp/0c07008b-0c30-43a6-b0e5-8caa79fb808c.sh
2019-11-22T13:53:59.1909722Z src/ci/scripts/install-msys2-packages.sh: line 9: pacman: command not found
2019-11-22T13:53:59.1969606Z 
2019-11-22T13:53:59.2059833Z ##[error]Bash exited with code '127'.
2019-11-22T13:53:59.2182503Z ##[section]Starting: Checkout
2019-11-22T13:53:59.2285166Z ==============================================================================
2019-11-22T13:53:59.2285259Z Task         : Get sources
2019-11-22T13:53:59.2285364Z Description  : Get sources from a repository. Supports Git, TfsVC, and SVN repositories.

I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact @TimNN. (Feature Requests)

@bors
Copy link
Contributor

bors commented Nov 22, 2019

💔 Test failed - checks-azure

@bors bors added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Nov 22, 2019
@pietroalbini pietroalbini deleted the rollup-mbxzl5c branch November 22, 2019 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rollup A PR which is a rollup S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants