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
Bugfix: Fix failing dev check in CRF #283
Conversation
This commit has the following changes: - A couple of dev check files in CRF did not have the label table creation in it. But the label table was consumed by one of the queries that led to dev-check failure. - Run dev check on Jenkins build instead of install check.
Refer to this link for build results (access rights to CI server needed): |
|
||
SELECT crf_train_fgen('train_new_segmenttbl', 'train_new_regex', 'crf_label', 'train_new_dictionary', 'train_new_featuretbl','train_new_featureset'); | ||
CREATE TABLE crf_label_new (id integer,label character varying); |
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.
The two files crf_test_small.sql_in
and crf_train_large.sql_in
have different indentation. Can we make them consistent
@@ -90,7 +90,7 @@ | |||
(18,'PRP$'),(19,'RB'), (20,'RBR'), (21,'RBS'), (22,'RP'), (23,'SYM'), (24,'TO'), (25,'UH'), (26,'VB'), | |||
(27,'VBD'), (28,'VBG'),(29,'VBN'), (30,'VBP'), (31,'VBZ'),(32,'WDT'), (33,'WP'), (34,'WP$'),(35,'WRB'), | |||
(36,'$'), (37,'#'), (38,''''''), (39,'``'), (40,'('), (41,')'), (42,','), (43,'.'), (44,':'); | |||
analyze crf_label; | |||
analyze test_crf_label; |
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.
Assuming that the table crf_label
doesn't exist, why wasn't crf install check always red?
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.
Couple of recommendations:
- Maybe move the jenkins changes to a separate commit since it's unrelated to crf changes.
- The commit message was a bit confusing to read, can we reword it ? I couldn't figure out why the test started failing from reading the commit message.
Thank you for the comments @kaknikhil . I moved out the jenkins build script to a different commit. |
Refer to this link for build results (access rights to CI server needed): |
This commit has the following changes:
in it. But the label table was consumed by one of the queries that led
to dev-check failure.