-
Notifications
You must be signed in to change notification settings - Fork 264
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
Move Windows CI to Github Actions #2334
Labels
Comments
This was referenced Dec 7, 2020
Most failures are due to extra uninits or other error reports, likely false positives. RtlCaptureContext is frequent: #2333. |
derekbruening
added a commit
that referenced
this issue
Dec 7, 2020
On a failure to match either the stderr summary or individual results, if the env var CI is set (true for Github Actions), runtest.cmake now prints out the contents of the results file(s). This greatly aids remote debugging of CI failures. Issue: #2334
derekbruening
added a commit
that referenced
this issue
Dec 7, 2020
On a failure to match either the stderr summary or individual results, if the env var CI is set (true for Github Actions), runtest.cmake now prints out the contents of the results file(s). This greatly aids remote debugging of CI failures. Issue: #2334
derekbruening
added a commit
that referenced
this issue
Dec 12, 2020
Sets up 3 jobs on Windows Server 2016 on Github Actions: + 32-bit debug build and tests + 64-bit debug build and tests + 32-bit and 64-bit release build plus drheapstat debug build, no tests Adds parameters to runsuite.cmake for the control split into these 3 jobs. Each job is roughly under 15 minutes. Each job downloads and installs ninja, doxygen, and WiX and uses VS2017. Adapts runsuite_wrapper.pl to use native Windows perl rather than Cygwin perl. No fork is available, so we tee the output to a file and read the file back in. Fixes a missed final line in the suite results processing. Adds default suppressions for invalid heap arguments (#2339) and leaks (#2340) in the VS2017 CRT. Generalizes test output for cs2bug and the suppress* tests in an attempt to get them to pass. Augments umbra_address_space_init() with a better error message to avoid cases like #2328 in the future. Shrinks the timeout to 60s for the failing umbra_client_faulty_redzone to eliminate several minutes of testing time just waiting for that test to time out; #2341 covers fixing it. Augments the test ignore list in order to get the jobs green. Issue: #2328, #2334, #2339, #2340, #2341
derekbruening
added a commit
that referenced
this issue
Dec 12, 2020
Removes the .appveyor.yml file as we have switched to Github Actions, which offers parallel jobs and auto-cancellation. Fixes #2334
derekbruening
added a commit
that referenced
this issue
Dec 12, 2020
Removes the .appveyor.yml file as we have switched to Github Actions, which offers parallel jobs and auto-cancellation. Fixes #2334
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Xref similar issue for DR: DynamoRIO/dynamorio#4131
With the loss of Travis we have moved our unix CI to Github Actions: #2323.
This covers also moving our Windows CI from Appveyor, to gain parallel builds and auto-prior-build cancellation (DynamoRIO/dynamorio#4585).
My first attempts are in PR #2326. The GA image we're targeting is Server 2016, the same as our attempt to update our Appveyor image in #2250 and PR #2265. Just like there, we hit major failures for 64-bit, due to #2328, which is now fixed; and major 32-bit failures: #2329. Both were DR problems and both are now fixed.
Now we're doing to a slew of test failures:
32-bit:
https://pipelines.actions.githubusercontent.com/tMvJIh3ZIUXIfOP7dfgG7UBvQKftGfP2Bp1gAjRieRAnDKBVqy/_apis/pipelines/1/runs/102/signedlogcontent/4?urlExpires=2020-12-06T21%3A21%3A31.3518373Z&urlSigningMethod=HMACV1&urlSignature=UM25pzPPpL5cFdRg9YFc7W%2B%2B4HA%2BYGaWei0XZiag1Ds%3D
64-bit:
https://pipelines.actions.githubusercontent.com/tMvJIh3ZIUXIfOP7dfgG7UBvQKftGfP2Bp1gAjRieRAnDKBVqy/_apis/pipelines/1/runs/102/signedlogcontent/5?urlExpires=2020-12-06T21%3A21%3A38.3981463Z&urlSigningMethod=HMACV1&urlSignature=DbjyahRfLoFQaxgIcCUoAJY4UAckE0LAGiBpBv7pclY%3D
The text was updated successfully, but these errors were encountered: