Skip to content

Retarget #1624 to a new branch #1642

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

Closed

Conversation

reuk
Copy link
Contributor

@reuk reuk commented Dec 1, 2017

This way, we can enable the cron job just for this branch, to check that it works as expected.

Copy link
Contributor

@chrisr-diffblue chrisr-diffblue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently this causes extra jobs to be started during CI, even if those jobs which is not the intention...

@reuk reuk force-pushed the reuk/cron-jobs branch 2 times, most recently from 6bca041 to ea147a0 Compare December 1, 2017 16:14
@reuk
Copy link
Contributor Author

reuk commented Dec 1, 2017

Two problems:

  • The build still takes longer than the maximum job time limit.
  • ASAN finds a mismatched new[]/delete in std::logic_error... maybe I'll try with a different version of clang/libc++

@owen-mc-diffblue
Copy link
Contributor

owen-mc-diffblue commented Jan 16, 2018

I asked @reuk about this yesterday and he said it would be better if other people took over his branches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants