-
Notifications
You must be signed in to change notification settings - Fork 161
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
Travis: run testinstall with all packages after testpackages #2835
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Of course, test with all packages fails now, but will hopefully be fixed by #2815. Perhaps you can cherry-pick this commit to the branch used for #2815, it will help to see it's effect, and then remove if from there before merging, so that we still will have two separate PRs.
I am going to update package archives tonight, if tests will go well, to give you latest Semigroups and some other updates since last week.
d033911
to
65a3043
Compare
Codecov Report
@@ Coverage Diff @@
## master #2835 +/- ##
===========================================
- Coverage 85.08% 72.43% -12.65%
===========================================
Files 695 628 -67
Lines 344362 314874 -29488
===========================================
- Hits 293002 228094 -64908
- Misses 51360 86780 +35420
|
@fingolfin please rebase this to see how the fix from #2815 will fare. |
I already rebased 2 days ago |
65a3043
to
ab49a9d
Compare
The build log from 2 days ago had lots of errors I cannot reproduce locally. So I have rebased this again now; and I'll also re-run local tests, with a pristine |
Ahhh, of course -- most of these errors are due to gap-packages/JupyterKernel#77 -- but @ssiccha and @markuspf made a new release yesterday, so I hope that once this is picked up by the package distribution, we are down to the handful of errors I am seeing locally. |
ab49a9d
to
ce0a281
Compare
@alex-konovalov Tests now pass here. However, I found another serious bug in the method reordering code that surfaces in |
56a3d5d
to
b5e5e79
Compare
This is currently passing. Would it pass if I merged it right now? |
@ChrisJefferson no - It should not pass because of the remaining issues after the method reordering (see #2818). This PR passes now only because it has 3 commits instead of one. As far as I understand, this is WiP, and before merge one of the commits should be removed, and another should be moved to a different PR. I've added the "don't merge" label to make it clear. |
@fingolfin please rebase this after #2869 has been merged, and remove the hack which disables some tests. |
b5e5e79
to
533c982
Compare
Two tests currently fail because of the broken XML:
|
@fingolfin The problem with building manuals is not present in the master branch. Please rebase. |
9026d4d
to
7437084
Compare
7437084
to
95e540d
Compare
95e540d
to
2a0b52e
Compare
I've rebased this now, and it there is on reported test failure before the tests hang for more than 10 minutes in
Looking closer at the hang, it might actually be related to the above test failure. |
2a0b52e
to
0495b64
Compare
@fingolfin can we try again this? |
0495b64
to
3b46442
Compare
Rebased |
3b46442
to
400fe86
Compare
The 64 bit version went fine through. For the ABI=32 job, all tests also passed. But for some reasons I cannot fathom right now, it failed in the coverage gathering step, see https://api.travis-ci.org/v3/job/485322346/log.txt resp. here:
Perhaps @ChrisJefferson has an idea? For now, I've added a change to show the content of the |
So I added that
So it seems we got a coverage file with > 2 GB data in it. My guess would be that the 32 bit version of GAP and profiling just are not able to handle that. Hence one option would be to simply apply this change only to the 64 bit version, but not the 32 bit version. That still serves our purposes, I think, and side steps the issue at hand. Thoughts? @ChrisJefferson @alex-konovalov ? |
400fe86
to
027760a
Compare
I think that's best. I'm quite suprised that coverage file loads in a reasonable time even in 64-bit GAP, but if it's working that's fine. Also, coverage files don't normally get that large, because they should only include each line once... |
Happy with 64-bit testing only. Shall we remove "do not merge" label? |
No description provided.